How VHS Replication Works
VHS replication uses a pull model for replication like all other CygNet services that support replication. In this model, one or many services may replicate data from a source VHS. The replicated services are responsible for pulling data from the source service, which relieves the primary VHS of the burden of replication and distributes it to the replicated services instead. This prevents replication from negatively impacting the primary active VHS.
VHS replication has similar constraints as other replicating services:
See Service Replication for information about replication and its configuration for other CygNet services.
Replication can be used as a method of backing up the history database without interrupting the source service. A replicated service could be stopped and its data files backed up. However, CygNet recommends enabling the creation of VHS Journal Files as a more viable backup solution. This method does not involve any disruption to either to the source or replicated VHS services. See VHS Journal Files for more information about this feature.
Note: If history data is thinned in a source VHS using the VHS Data Thinner utility, these deletions will also be propagated to the services replicating from this source.
Note: See VHS Data Forwarding for more information the VHS Data Forwarding feature, which allows history data to be copied and pushed from a source VHS to up to three destination services.
Note: The VHS fully supports the replication of extended data types and binary large objects (BLOBs) from one VHS to another. This includes the replication of dynagraph cards and the DynaCard Library used by the ForeSite Product Optimization Platform.
More:
Replication Missed Change Events
|
|
|
